Overview
What is Heroku Platform?
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric approach for software delivery, integrated with developer tools and workflows. It’s three main…
Every day more disappointing
Great for startups
Great for early stage products
Amazing value for a freelance/contract application web developer
A great option for your initial deployment!
Heroku: perfect platform for agile teams!
Almost Zero Learning Curve!
Heroku Helps Us Get Things Done
Heroku most developer-friendly platform
Perfect for small projects
Heroku Makes Back end Management Simple
Heroku, a solid cloud-offering from Salesforce
Beginner to moderate, it will be your Hero-ku ;D
The easiest platform as a service Rails app hosting solution that our developers love using
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Upgrades and platform fixes (43)8.484%
- Scalability (43)8.282%
- Platform management overhead (42)7.676%
- Platform access control (42)7.070%
Pricing
Production
$25.00
Advanced
$250.00
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $85 per month
Features
Platform-as-a-Service
Platform as a Service is the set of tools and services designed to make coding and deploying applications much more efficient
- 7.6Ease of building user interfaces(26) Ratings
Ability to build flexible user interfaces using drag-and-drop tools
- 8.2Scalability(43) Ratings
Ease of scaling up or down to meet demand
- 7.6Platform management overhead(42) Ratings
Resources required to keep platform up and running
- 8.3Workflow engine capability(29) Ratings
Process automation using rule-based engine
- 7Platform access control(42) Ratings
Rules controlling what data different user categories can access
- 8Services-enabled integration(41) Ratings
Ability to integrate with cloud applications and data via APIs and pre-built connectors
- 8.7Development environment creation(38) Ratings
Ease of creating new development environments
- 8.6Development environment replication(37) Ratings
Ease of replicating new development environments
- 8.2Issue monitoring and notification(41) Ratings
Integrated monitoring and notification of issues and problems
- 8.4Issue recovery(38) Ratings
Ease of recovery from problem state
- 8.4Upgrades and platform fixes(43) Ratings
Ease of deployment of major upgrades or problem fixes
Product Details
- About
- Competitors
- Tech Details
- FAQs
What is Heroku Platform?
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric approach for software delivery, integrated with developer tools and workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like Git, GitHub or Continuous
Integration (CI) systems without the need to manage infrastructure.
The web-based Heroku Dashboard makes it possible to manage applications online
and gain visibility into performance.
Heroku Operational Experience (OpEx)
OpEx helps developers troubleshoot and remediate issues and
customize the ops experience to identify and address trends in application health. Heroku provides a set of tools to alert teams if something
goes wrong, or to automatically scale web dynos if the response time for web
requests exceeds a specified threshold.
Heroku Runtime
Heroku runs apps inside dynos—smart containers on a fully managed runtime
environment. Developers deploy their code written in Node, Ruby, Java, PHP,
Python, Go, Scala, or Clojure to a build system which produces an app that's
ready for execution. The system and language stacks are then monitored,
patched, and upgraded. The runtime keeps apps running without manual
intervention.
Heroku Platform Competitors
Heroku Platform Technical Details
Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Unspecified |
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(171)Attribute Ratings
Reviews
(1-25 of 28)Great for early stage products
- Server hosting.
- Database hosting.
- Pricing - more expensive than other modern options.
- Marketplace add-ons sometimes change with little notice.
The convenience does come with a cost, and at scale, it's more expensive than other options we've looked at more recently. Overall, we've been happy with Heroku as a platform.
- Easy to use
- Fairly cheap to start with
- Fairly easy to scale the application server
- Not 100% reliable on the cheapest plan; we've had a couple instances of downtime over the year
- Limited number of supported languages
- Limited choice of database
Heroku: perfect platform for agile teams!
- Continuous deployment via repositories
- Abstraction of computing resources
- Add-ons mechanism (databases, message-queue services, etc.)
- Some Heroku-specific errors are hard to debug
Heroku Helps Us Get Things Done
- Great APIs: Heroku's APIs are extremely useful and always improving.
- Developer-friendly documentation: Heroku's docs are thorough and well-written.
- Great Customer Support: Heroku's front-line support is great, and knows when to escalate directly to people working on the product.
- Heroku Metrics is great, but we'd love to see direct API access (and the ability to add and customize our own metrics).
- Heroku's status/downtime/maintenance notification system could be improved with better granularity to help filter irrelevant alerts.
At the other end, I'd imagine that larger organizations who have in-house staff doing DevOps might see a lot of duplication between those staff and what Heroku is doing to add value. At some point, the premium you're paying Heroku would probably prompt you to move those functions or keep them in-house.
Heroku Makes Back end Management Simple
- The push to deploy almost always works and is very smooth and seamless.
- The Heroku add-ons have always been very reliable and easy to install.
- Their documentation is very thorough, and they have built a mechanism using buildpacks to make their platform very flexible.
- Some features that can be critical for security are hidden behind their Enterprise offering.
- The product is much pricier than using cloud providers like AWS, Azure, or Digital Ocean. It does solve a lot of Dev-Ops headaches, but may be too expensive for some companies.
- Some logging and auditing functionality is also somewhat hidden behind the Enterprise offering, where many other platforms offer this out-of-the-box.
The easiest platform as a service Rails app hosting solution that our developers love using
- Ease of configuration and scaling.
- Ease of code deployment.
- Ease of deploying staging environments.
- An ephemeral file system may require workarounds certain developers are not used to.
- The cost is high and can easily balloon as you grow if you aren't careful.
- While configuration is super simple, it will not be as flexible as bare metal servers.
If you already have a bare-metal solution that has scaled well with your own DevOps team, then moving to Heroku later would likely only introduce a higher cost without many other benefits.
The best place I know to deploy a brand new Rails app
- The tooling is simply amazing. You can deploy your application in some minutes without any prior experience with the platform.
- Their way of building applications encourage you to think about scalability and composability of your app.
- They have a big community around the platform and many add-ons written by third-parties.
- The price is not so affordable when you start growing. For small companies, needing small containers, it works quite well but for large applications, it may be too expensive.
An amazingly easy deployment and hosting service
- Easy to use
- Easy to deploy services
- Easy to add plugins
- Could provide a bit more customization
- Could be a little easier on the pricing side
- Could provide better insight tools
It's not great if you want ultimate control over all those aspects.
Heroku - Great for quick projects
- Quick to get started
- Countless Integrations
- CLI is easy to use
- The cold start times can be brutal for free plans
- Cost can be expensive if you have many dynos
- Have to be careful of third party integration pricing as well
Perfect for Hobbyists and Beginners
- Free Option is great for people just learning or wanting to make simple apps
- Very easy to create several environments for your app in no time with exact clones
- Documentation is easy to follow and full of tutorials
- If you're not careful, you can easily create an expensive app by accident.
- Inconsistant experience with all the other add-ons. Some are not documented well.
Quick to Set Up and Experiment With
- Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
- The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
- Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.
- Heroku can get pricey pretty quickly as you scale.
- The quality of add-on vendors is increasingly variable as Heroku expands the marketplace.
Easy Deployments
- Easy deployments
- Variety of quality add-ons
- Good UI/UX
- Autoscaling
- Cost
- Support for React
In summary, if you want brain-dead simple hosting for popular web frameworks like Ruby on Rails, NodeJS, to this day nobody beats Heroku.
- Amazingly clear and straightforward documentation (versus the quagmire of AWS docs).
- Deploy your entire site in one command.
- Setting up asynchronous job processing for long running operations (e.g. sending emails, making external API calls).
- A wonderful portfolio of tightly-integrated add-ons in their marketplace.
- Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
- Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
- Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.
You Get What You Pay For
- Incredibly straightforward deployment processes with best-in-class documentation and getting started tutorials
- Great reporting and analytics
- Transparent pricing lets you get really good estimates on how much hosting will cost, so there aren't any surprises
- Easy to enable and disable plugins
- Autoconfiguration and "convention over configuration" for most features
- The vibrant community means it's easy to find out how to achieve various goals by seeing what others did
- Top notch support that fixes problems right away
- Relatively affordable given what value-added features you get
- Could be less expensive, although you get what you pay for
- Sleeping apps can be an annoyance: Heroku automatically puts your apps in sleep mode and they have to spin back up after periods of inactivity. Much of this can be solved but it requires working around the built-in functionality. I understand why they do it but it's an area that could be improved.
- Restrictions to server access means you can't customize as much as you could if you owned the server. But again, this is also a benefit because it's about convention over configuration. So you can't configure as much, but then, you typically don't have to.
Heroku the all in one cloud platform service
- Supports auto deployment using the GIT version control system
- Free SSL for custom domains
- Easy to customize server needs
- Pipelines help to stage the application
- Has inbuilt application for accessing and managing the servers from the terminal
- Add-ons are pretty costly
- Limited server locations
- Prices are costly
Easy to use and the best documentation around!
- Third party integration
- Separation between staging and production sites
- Documentation
- Terminal commands
- Scalability
- Frequent maintenance from Heroku team which forces lack of productivity from my team
- Adding dynos - not very cost effective
Heroku FTW for POC!
- Works well with GIT making deployment pretty easy.
- A variety of add-ons to that offer various additional features.
- Multiple language support (RoR, Java, etc.)
- Stability. Heroku seems to suffer from stability issues from time to time.
- Logging. I know that there are a number of different options out there. I just don't want to pay extra for something that is a pretty basic requirement.
- The web based UI is pretty sparse. I appreciate the simplicity (having used AWS and Azure). That said, I sometimes have trouble finding things... like how do I get to my running app?
Deploy Apps Faster on Heroku
- Highly scalable
- Easily traced activities and version control
- Optimized for team development
- Needs more docker services
- Would be nice to have a unified DX for Salesforce developers/administrators who are working with Heroku
Heroku, the good, the bad and the ugly
- Heroku's deployment process is very painless.
- Heroku does a great job of making system/infrastructure upgrades painless and transparent.
- Heroku's CLI toolset is well built and puts all of your app's info, settings, add-ons, logs, etc, right at your fingertips.
- Heroku does not offer a very wide range of dyno sizes - it would be nice to be more flexible about how much RAM or CPU each dyno consumes.
- While Heroku is well engineered for deploying certain common types of applications, it can be tricky to deploy more esoteric or uncommon configurations (like Rails + Node.js at the same time).
Heroku is really, really good for Ruby on Rails applications. Heroku is not very good for applications that require many different languages for various micro-services, or the types of apps where you might have a very tiny service that does not require much RAM or CPU, but which you need to spin up hundreds of such instances.
Heroku would probably be good for a slightly technical client if you were going to turn over the keys after a consulting gig - it is very well documented and there are many resources out there for dealing with specific issues, it is way better than trying to support your client on something like DreamHost or GoDaddy.
Perhaps Heroku's greatest strength is in providing a hosting platform that stays out of the way while you build out your business logic and grow your startup from the beginning. It allows your engineers to focus on the problem, not the infrastructure.
- I can't stress enough the importance of Heroku's integration with a wide variety of providers in the form of add-ons. Provisioning is easy for logging and monitoring, caching, data storage, text messaging, email, source code hosting, payment processors, performance and load testing, different database add-ons, etc., -- if you can think of it, Heroku probably supports at least one type of provider for it. This alone saves a ton of time evaluating and integrating the different providers into your application.
- Heroku is insanely well-equipped to host Rails applications and other Ruby-based web applications (e.g. Sinatra and custom Rack applications). They also support PHP, Node.js, Python, Java, Go, Clojure and Scala-based applications.
- The Heroku Dashboard is one of the best UIs I've seen for just about anything. Given how complicated it could get, it's obvious what you are doing and how to do it.
- The Heroku documentations is top-notch and always kept up-to-date. I am VERY picky about this sort of thing and I have no complaints at all.
- I've found customer support to be variable. When I've contacted them by filing tickets, they have been professional and generally very responsive, however, when we set up a phone conference to discuss our security needs, the support person we talked to was only marginally professional in his responses, and not really helpful.
- Heroku needs more than one hosted location in the US. Relating to the meeting I mentioned, my previous company needed a disaster recovery plan since we were trying to qualify for SOC-2 certification. Because we were also a fintech business, we could not choose a host outside of the US, so having only Virginia as an available location caused problems for us.
- Easy to get started -- you just need some git experience.
- Reliable - over the years our sites have rarely been down. When they are down due to our own code (memory limitations, bugs), they're restarted in a smart way that brings them back fast.
- Database management using Postgres is made extremely easy. As someone who's not a sysop, I setup database replication, made and restored backups, connected from my local computer, and did many other things with surprising ease.
- For personal sites and small sites, the price can be daunting. For the same price as a worker, and an addon or two, I could get a full out server.
- Better reporting on how apps scale and whether I should add more dynos or less. At times our site was growing slower and slower and we upped our dynos. It wasn't until we lowered our dynos that the site sped up.
- The "heroku" plans on the addons are sometimes confusing to understand how that works if I transition off Heroku.
Heroku to me is less suited for companies that have a dedicated sysop who can handle server architecture and maintenance. Once our site was large enough, we found we could save more than the cost of an entire hire by switching to dedicated servers. For these very large sites, I feel like heroku could do better from a pricing standpoint.
I feel it's better for smaller sites that might be in the under $1,000 range, or for companies that have the cash and want to move fast.
Heroku for data processing, fast & easy
- Fast: We can get web apps up and running very quickly.
- Add-ons: Heroku has a rich add-on library that further saves a lot of time we would spend building things from ground-up.
- Simple: GitHub integration and clean UI makes the learning curve relatively flat.
- Docs Organization: I think the docs are good, but they could definitely be organized better.
- Heroku CLI: Some of the commands feel unintuitive.
- Scaling: I haven't really seen a great solution to scale dynos based on need.
Heroku rocks!
- Easily deploy.
- Review apps!
- Add members easily.
- Managing dynos (had to use third party service).
- Analytics could be a bit better.
Heroku: Pay to make your DevOps work go away
- When you have an app that closely follows the conventions of its framework (say, a conventional Rails app), Heroku makes it stupid simple to get a production website going.
- Setting up sandboxes and test apps is simple. Because you can associate add-ons and databases to Heroku apps, you can copy an entire environment quite easily.
- Heroku recently added the ability to auto-deploy from GitHub pending Continuous Integration results, make it easy to set up a Continuous Deployment flow through GitHub.
- When you have elements outside of the norm, things can get harder. For example, our Rails app depended on a non-Gem dependency (Pandoc), and figuring out how to get Heroku to play nice with that was rather difficult. Along the same lines, doing something like a combination Node/Rails app requires quite a bit of finesse to get Heroku to do what you want.
- Heroku is much pricier than something like EC2 for the amount of computing power. We had lots of problems with memory usage with our app. On EC2, we could have simply moved to larger instances, but on Heroku we had to go on a bit of a goose chase to find ways to reduce memory usage. It's necessary to assess scale and decide whether the reduced complexity is worth the cost. In my uses of Heroku, it has been.
- You are at Heroku's mercy when they have an outage, and there's generally nobody to talk to.
Heroku - A Great Choice for Developers Needing Quick Deployment
- Easy to deploy.
- No need to manage infrastructure on your own.
- Lots of third party add-ons.
- There are no regional dependencies that you can control unlike AWS.
- Locked into their platform.
- No easy way to migrate to a different platform.